{graveyard}/qt-labs/vscodeext.git/qt-ui/src/util.ts, branch dev

qt-ui: Check also for `qmake.bat` in the Qt installation directory

2024-12-18T09:13:24+00:00

Some Qt installations do not have `qmake.exe` but `qmake.bat` instead.
This commit adds a check for `qmake.bat` in the Qt installation
directory.

Fixes: VSCODEEXT-117
Change-Id: I2d4aa5fdda216739be16bc3a95867496d2817561
Reviewed-by: Joerg Bornemann

qt-ui: Add special lookup place to find Designer for vcpkg

2024-11-21T13:33:08+00:00

On some platforms, Designer is not located in any of the qtpaths keys
directly. We also need to check `tools/qttools/bin` for Designer.

Change-Id: I0a49868262019654d6fd8aebbc9be76fb9f3da20
Reviewed-by: Marcus Tillmanns

Add missing qtpaths features

2024-11-01T14:38:23+00:00

* Remove `getSelectedQtInstallationPath()` use `getSelectedKit()` instead
Since we support both root installation kits and qtpaths, we cannot just
return the installation path of the selected kit. We need to return
the all kit information.

* Use only qtpaths exe paths to cache information
Since we store only qtpaths exe paths in `cmake-kits.json`, we don't
need to hash it with other values like name or isVCPKG. And also, we can
improving the performance by caching different kits but with the same
qtpaths.

* Implement `qt-cpp.qtDir` for debug templates on Windows
We have to return possible dll paths for qtpaths kits.

* Deprecate `qt-cpp.kitDirectory` and use `qt-cpp.qtDir` instead
We support both root installation kits and qtpaths. So we cannot just
rely on `qt-cpp.kitDirectory\bin` in debug templates. For qtpaths, we
need to return multiple paths.

* Remove `kit-directory.ts` and move content to `launch-variables.ts`

* Add `qt-cpp.qpaPlatfromPluginPath`
When we debug with Qt from vcpkg. We get the
`could not find or load the Qt platform plugin "windows" in "",` error
if we don't set the `QT_QPA_PLATFORM_PLUGIN_PATH` environment variable.
That's why we need to set `qt-cpp.qpaPlatfromPluginPath` according to
`cmake.buildType` either `debug` or `release` path.

* Locate Designer via qtpaths
To support using Designer from qtpaths, we need to locate the Designer
inside paths like `QT_HOST_BINS`, `QT_HOST_LIBEXECS`,
`QT_INSTALL_LIBEXECS`

* Remove error messages when a qtpaths kit selected
In the previous implementation, we showed an error message when a
qtpaths kit selected instead of root installation kits.

* Add Qt version detection from qtpaths

* Add selectedQtPaths to coreAPI
When a qtpaths kit is selected, we set `selectedQtPaths` to inform
other extensions.

* Move `queryHostBinDirPath` to `qt-ui/util.ts`
Since it is only used in `qt-ui`, we move it to `qt-ui/util.ts`

* Shorten `locateQtDesignerExePath()` to `locateDesigner()`

* Use `set designerClient()` and detach inside it
It is better encapsulation.

Task-number: VSCODEEXT-86
Task-number: VSCODEEXT-93
Task-number: VSCODEEXT-92
Change-Id: I0aadd4dd5e2f9508576dda70d24eb14de7796a86
Reviewed-by: Marcus Tillmanns

Style: Shorten the exe suffix variable

2024-10-07T08:16:25+00:00

Change-Id: Id7b61cc70c97b3e859a0004bb206e970ca51f17e
Reviewed-by: Marcus Tillmanns

qt-ui: Use QT_HOST_BINS to detect designer

2024-08-09T14:33:26+00:00

When a kit which do not have binaries is selected, `qt-ui` cannot locate
the designer binary because the binary is inside some specific kit
folders like `gcc_64` in Linux or `macos` in MacOS. `QT_HOST_BINS`
should be used to prevent that.

* Move `queryHostBinDirPath()` into `qt-lib`
* Enable `queryHostBinDirPath()` in `locateQtDesignerExePath()`

Change-Id: I5199ca56832b1372ffe7a1ee6c683b32a61089cb
Reviewed-by: Marcus Tillmanns

Remove unused function

2024-07-24T13:11:03+00:00

Change-Id: I3dfc89485b9269b29266a47116a827ca219a48df
Reviewed-by: Marcus Tillmanns

Divide the monolithic extension into modular extensions

2024-07-18T12:36:12+00:00

The below Extensions are created with this commit:

* qt-core
* qt-official
* qt-ui

qt-core

This extension is the core extension for the Qt extensions.
It provides the basic functionalities for the other extensions to work.

* It handles the communication between the other extensions.
* It provides the basic functionalities and common features for the other extensions.
* The all other extensions depend on this extension.

qt-ui

This extension provides the UI functionalities.

* It communicates with the `qt-core` extension to get information about the Qt Widget Designer.
* It provides syntax highlighting for `.ui` files.

qt-official

This extension has the rest of the previous monolithic extension functionalities.
It should be divided into more extensions in the future.

This commit implements:

* Common functionalities are moved from `qt-official` to `qt-core`.
* `qt-lib` is implemented as a npm module to gather the common code.
* Static analysis tools for every extension are added.
* Updated all `package.json` files to reflect the changes.
* `ci-scripts` is implemented to run the static analysis tools and tests.
* The `common` is created to gather the common code for tools.
* Extension packs are updated.
* The `ThirdPartyNotices.txt` files are generated for every extension.
* The `README.md` files are updated to reflect the changes.
* `.vscode/launch.json`, `.vscode/extensions.json`, and `.vscode/tasks.json` are updated.

Change-Id: Iac9b7e071275e92cdfbb3a47fba24d3ba8e41c89
Reviewed-by: Marcus Tillmanns
Reviewed-by: Leena Miettinen